DataServer configurations
The OpenEdge DataServer for ORACLE supports many possible configurations. There are two general types of configurations—local and remote—with several variations on each type:
- Local DataServer — All the DataServer software modules run on one machine. Your ORACLE database can also run on this same machine, or it can run on a separate machine that you access through ORACLE Networking.
- Remote DataServer — The DataServer software modules run on different machines. Typically, the client module runs on one machine and the DataServer module runs on another. The machine on which the DataServer module runs is called the host machine. The host machine and the machine where the client is running can communicate through OpenEdge networking (TCP/IP).
Figure 1–4 shows a local DataServer configuration where all the modules run on one machine. In this case, the ORACLE database is also local.
Figure 1–5 shows a local DataServer accessing an ORACLE database on another machine through ORACLE Networking. You must install ORACLE Networking on the client machine. In configurations that include ORACLE Networking, there are no OpenEdge processes running on the machine where the ORACLE database is running.
Figure 1–6 shows one possible configuration for the remote DataServer where a client accesses a remote DataServer for ORACLE. Here, the ORACLE database and the OpenEdge DataServer for ORACLE are running on the same machine.
OpenEdge handles the communication between the client and the DataServer. The client and server processes that make up the DataServer adapt to a variety of network configurations.The previous illustrations showed a few possible configurations. Table 1–1 lists all supported configurations. It considers possible client/server combinations and networking options.